* feat(app): add enable status light section to robotsettings

…ttings found (#13654)

Closes RQA-1231 and RQA-1228

* fix(app): fix running command list highlight issue

Lowercase the robot's current run status if a status header is rendered. This is made cleaner by
adding a lowerCase format option to our i18n interpolation.

* fix(app): fix protocolsetup next step button issue

…ly eat the other brokers? (#13647)

Closes RQA-1648, RQA-1649, RQA-1646, RQA-1652, RQA-1645

Fixes various punctuation, casing, and missing errors on the desktop app/ODD.

closes RQA-1214

…T-2 deck recalibration (#13642)

Closes RQA-1324

Closes RQA-1513, RAUT-750, RQA-1686

Provides fixes for tearing snackbars & protocol command animations, magblock "is not connected" chip display, and flashing "firmware update" screens during wizard flows.

fix RQA-1575, RQA-1515, RQA-1380

… and opentrons.execute.execute() (#13629)

)

This adds a file that lives in the deploy bucket that tracks past
releases of the app. We can use this for autogenerating previous-release
pages and is a good thing to have. We can also use it for release
revocation if we want.

* fix(app): add null-check to all options without odd

…mgs (#13680)

closes RUXD-1109

closes RAUT-768

On the mount gripper step, we want to display a 'Need help?' link, but not a 'back' button. On the
first pin attachment step (front jaw), we want to remove the 'back' button.

We removed the urls for the old OT-2 infrastructure, because we don't
want them anymore. But because we removed them from the app config, and
the app doesn't downgrade configs, then if you
- ran 7.0, the config gets deleted
- run 6.3.1 or previous, the config never gets restored
and the app just doesn't know where to get robot system updates and
therefore acts as if there are none. That in turn means you can't
downgrade your robot through the app, you have to manually update from
zip.

The gross but only solution is to change the config back to get those
values to be present again when you downgrade. This leaves a historical
hole - someone who ran 7.0.0 and downgraded to 6.3.1 would still have
that behavior - but it's fixed going forward, and those affected can
just remove their app config.

When something hits /settings/pipettes, we load known mutable
configuration overrides. So if you don't have any for the attached
pipettes, we don't return anything.

The thing is, what we actually want is to return all of the mutable
configurations, with overrides applied. So now we do.

Closes RET-1376

…3710)

closes RAUT-772

* fix(app): fix calibration result summary condition issue

* refactor(app-shell): perform protocol migration if pre-parity v7.0 protocols folder exists

Migrates protocols to the protocols directory if protocols_v7.0-supported directory exists.

Notable changes:

* Rework `simulate.py` to support PAPIv≥2.14 protocols, via Protocol Engine. This rework mirrors what we did to `execute.py` in #12970.
* Rework the `adapt_protocol_source()` helper to cope with protocols for which we don't know the filename. This is necessary to support `opentrons.simulate.simulate()`, whose `filename` argument is optional.

  Unfortunately, this requires modifications to `opentrons.protocols.parse` to make the filename more pass-through, so `adapt_protocol_source()` can tell when it wasn't provided.

Plus various smaller refactors for type safety, deduplication, and consistency.

#13760)

Block a protocol run if bad calibration data for any required module to mirror pipette checks before
a protocol run

Co-authored-by: Jeremy Leon <[email protected]>

…help text (#13766)

* added taskification of hardware control movement commands to execution manager wrapper

…tion in pipette command text (#13756)

fix RQA-1770

Removes overflow: hidden from the shared styles within the pipette slideout. The top-most slideout
ancestor component requires overflow: auto to prevent undesired resizing after selecting a form
checkbox.

#13762)

Former decoy inside of test did not account for addition of robot type feature flag to door safety switch, other feature flags may make use of this in the future

…3731)

These parameters were in place during a stage in development when the two had yet to fully separate. Adapter ID also removed from V7 due to deprecation.

closes RQA-1705

* refactor(app): remove unused robot restart timeout logic

Removes the redux layer robot update restart timeout logic that is replaced by more generalized
robot update flow error handling.

* refactor(app): refactor robot update failure message

…deout (#13771)

closes RQA-1768

fix RQA-1789

The flex doesn't store its serial number in /var/serial; instead, it
stores it in an onboard eeprom. While we had the code to read it, we
weren't using that code anywhere, and we should expose it to the app for
display.

However, the update server doesn't (and shouldn't) know how to talk to
the onboard eeprom. That's a problem, because it knows perfectly well
how to read a file, and thus is the current source of truth for the
serial.

So this PR
- adds the serial to the robot server health endpoint, on both ot-2 and
flex
- changes the app to try and prefer the serial from the robot server
health endpoint, falling back to the update server health endpoint if
necessary

…sults step (#13792)

* fix(app): fix pipette wizard flows always showing "recalibrate" on results step

Persists hasCalData between renders so as not to return true during the attach/calibration wizard
flow after the calibration step.

#13794)

These need to get uploaded to pypi and were not because of some kind of
version conflict in api. With a bit of judicious pipenv relocking all is
well.

…13795)

fixes RQA-1705

closes RQA-1805

Some combination of pydantic and fastapi (fastapi, I'm pretty sure, due
to things like pydantic/pydantic#1223 )
conflate "null" and "not present" in weird ways. This means that in the
health response pydantic class,
- If you create robot_serial in the proper way to have a pydantic field
that can be either a string or null but must always be passed in to the
constructor - annotation Optional[str] and do not provide a default -
then pydantic will say there's a field missing if you explicitly pass
in null (the bug this fixes, since this 500s the route)
- If you create robot_serial with a default value, which is _not
correct_ because there is no default, then something (probably fastapi)
will remove the _key_ from the model rather than issueing it with a
null, which is terrible, but is better than the other way I guess.

Updating fastapi might help with this maybe. I don't know.

…er on heater shaker module (#13803)

Properly combine dynamic logic for opening the heater shaker latch and offloading the labware and
adapters in the correct order during LPC checks of labware on adapters on heater shaker modules

Closes RAUT-803

Co-authored-by: Shlok Amin <[email protected]>

…omplete (#13809)

Ensure that all queries for /calibration endpoints (OT2 only) are invalidated upon completion of any
of the three OT2 calibration flows.

Closes RQA-1814

Co-authored-by: Shlok Amin <[email protected]>